docs(release): prep stable 0.3.0 (changelog + counts)#433
Merged
Conversation
Make main release-ready for the stable 0.3.0 cut (per docs/RELEASING.md). Does NOT release — merge + dispatch Publish is a separate step. - CHANGELOG.md + packages/ui/CHANGELOG.md: move [Unreleased] → dated [0.3.0] - 2026-06-16 (the publish workflow greps `## [0.3.0]`), drop the now-satisfied pre-release notes, add a Fixed entry for the theme-adaptive CandlestickChart/SparklineGrid colors, add the v0.3.0 link reference, and open a fresh empty [Unreleased]. - Fix stale component counts 144 → 225 in README.md, packages/ui/README.md, docs/ARCHITECTURE.md. - ROADMAP: status planning → release prep; link the real 0.3.0 milestone. - RELEASING.md: document the apps/registry version bump, the doc-sync step, and the post-publish PUBLISHED_VERSION flip (registry install target must advance only after the version is live on npm latest). Deliberately NOT flipping PUBLISHED_VERSION here — that stays ^0.2.1 until 0.3.0 is published, else the deployed registry would advertise an unpublished version and break `npx shadcn add`.
|
ntk preview
Built from |
…ts, sidebar fix, react-doctor sweep - CHANGELOG (root + packages/ui): add BREAKING React 19 requirement (drop React 18, forwardRef -> ref-as-prop, useContext -> use), the 70 new components (forms 18, motion 37, core 7, charts 5, AI 3), the docs-sidebar category fix, shared-internals extraction, and the react-doctor warning sweep; re-date to 2026-06-17. - Component count 225 -> 295 across README (root + package), ARCHITECTURE, ROADMAP metric.
Collaborator
Author
…309) Resolves the CHANGELOG conflict and brings the release-prep branch up to date with everything that landed on main since it was authored (React 19 migration, core/forms/charts/motion families, count-derivation #450). - Component count corrected everywhere to the registry-derived 309 (was 225/295 across CHANGELOGs, READMEs, package.json, ARCHITECTURE, ROADMAP). - ROADMAP headline counts recomputed (+169 net from the 140 baseline); curated list relabeled as a highlight subset. - 0.3.0 changelog dates refreshed to 2026-06-26. - component-count.test.ts: assert the *newest* CHANGELOG count snapshot (not strictly [Unreleased]) so the drift guard survives a release cut — after this PR the count lives in [0.3.0] and [Unreleased] is empty. Claude-Session: https://claude.ai/code/session_01KB2yTDBo7Knydqvz1VvFdF
…lint The added comment used "just" and "immediately", which the registry's write-good-comments ESLint rule rejects. Reworded without weasel words. Claude-Session: https://claude.ai/code/session_01KB2yTDBo7Knydqvz1VvFdF
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #432
Makes
mainready to cut stable 0.3.0 (perdocs/RELEASING.md). Docs + one test-guard tweak — this PR does not release. Merge → dispatch Publish is the separate next step.Changes
CHANGELOG.md+packages/ui/CHANGELOG.md):[Unreleased]→ dated[0.3.0] - 2026-06-26(the publish workflow's release gate greps## [0.3.0]), dropped the now-satisfied pre-release notes, added the granular 0.3.0-train families (form primitives, charts/dataviz, AI/core primitives, motion/effects), a Fixed entry (theme-adaptiveCandlestickChart/SparklineGridcolors), thev0.3.0link reference, and a fresh empty[Unreleased].registry.items.length(= 309 after fix(registry): derive component count from registry, drop hardcoded 225 #450). Synced every prose surface that drifted:README.md(×3),packages/ui/README.md,packages/ui/package.json"description",docs/ARCHITECTURE.md, and the ROADMAP. (The earlier 144→225 / 295 numbers are superseded.)planning→release prep;milestone TBD→ real 0.3.0 milestone; headline counts recomputed to +169 net (140 → 309); the curated component list is relabeled as a highlight subset (it enumerates the first ~85, not all 169).apps/registryversion bump, the full doc-sync step (now incl.packages/ui/package.jsondescription + the count-guard test), and the post-publishPUBLISHED_VERSIONflip.apps/registry/lib/component-count.test.ts(added onmainby fix(registry): derive component count from registry, drop hardcoded 225 #450): the guard asserted the count lives in[Unreleased]. Cutting the release moves it into[0.3.0]and empties[Unreleased], which would break that guard. Retargeted it to assert the newest count snapshot in the changelog (first match, file is newest-first) — works both between releases and immediately after a cut. Still pins toregistry.items.length.Deliberately NOT here
PUBLISHED_VERSIONflip. It stays^0.2.1until 0.3.0 is live on npmlatest; flipping before publish would make the deployed registry advertise an unpublished version and breaknpx shadcn add. Documented post-publish follow-up.packages/uiandapps/registryare already0.3.0.Verification
Count guard simulated against the real files (no local
node_modulesin the branch worktree; CI runs the real suite):CHANGELOG.mdcount snapshot = 309 ==registry.items.lengthhome/{en,fr}.mdxcount claims all = 309main)Release sequence after this merges
0.3.0-canary.<sha>).main→ tagsv0.3.0, publishes--tag latest, GitHub Release.PUBLISHED_VERSION→0.3.0+ regenerate registry (drift/integrity guards verify it).